Every ChromIQ project lives in its own folder (inside ~/ChromIQ, or your custom output folder from Settings), named after the profile. Everything you would print, install or keep sits right at the top of each run folder; the paperwork is grouped into a few folders whose names already tell you whether you care about them. Each build is a “run” (runs/run1, run2 …); a run's profiling work sits in the run folder, and any later checks of the finished profile — “verification” runs — accrue as dated folders inside verifications/, kept apart so the two never mix. Below: first the three files that matter, then what each folder means, then every file in detail. “CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26” stands for your profile's name.

=== PROJECT FILE STRUCTURE ===

CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26/                         Your project folder, named after the profile. One per printer,
│                               paper and instrument combination you profile.
├─ project.json                 ChromIQ's own note of which runs exist and which one you are
│                               working on. Small, and best left alone.
├─ Where are my files.txt       This guide, as a plain text file, refreshed whenever the
│                               layout changes. Yours to read, edit or delete.
├─ cal/                         The optional printer-calibration target and the curves
│  │                            measured from it, shared by every run in this project.
│  ├─ chart/                    A copy of the calibration chart exactly as it was printed,
│  │                            kept from the moment you start measuring it — “Restore Used
│  │                            Chart” puts it back.
│  ├─ old/                      Earlier calibrations, each in a folder named with its date.
│  │                            Making a new calibration chart moves what was here rather than
│  │                            deleting it, so you can always go back to one.
│  ├─ exports/                  That calibration chart's hand-off files for other programs.
│  └─ reports/                  The measurement reports of this project's calibration, made
│     │                         with Run type Calibration. Created by the first one.
│     └─ old/                   Earlier versions of those reports, moved here by an Update or
│                               by “Delete Selected Report”, never deleted.
├─ exports/                     Files made for other programs from the Tools menu, belonging
│                               to the whole project rather than to one run.
├─ reports/                     Measurement reports that cover the whole profile rather than
│                               one run — see the Measurement Report row in the next section
│                               for which reports folder a report lands in.
├─ old/                         Reports that covered several runs of this project and were
│                               removed with “Delete Selected Report”, each in a folder named
│                               with the moment it happened. Moved here, never deleted.
└─ runs/                        One folder per profile build. This is where nearly everything
   │                            lives.
   ├─ run1/                     The first build: its chart, its measurement, its profile.
   │  │                         run2, run3 … follow the same shape, and the newest is the one
   │  │                         ChromIQ is working on.
   │  ├─ chart/                 The copy of the chart this run was measured with, kept the
   │  │                         moment measuring starts. “Restore Used Chart” puts this back.
   │  ├─ reads/                 Your individual readings, when you measure one chart several
   │  │                         times to average them.
   │  ├─ reports/               What ChromIQ tells you about this build: quality checks, the
   │  │                         re-measure list, and the dated measurement reports.
   │  ├─ exports/               This chart's files for other programs — the i1Profiler patch
   │  │                         set and the plain colour list.
   │  ├─ cache/                 Working files from the tools. Always safe to delete: ChromIQ
   │  │                         can make all of it again.
   │  ├─ old/                   Measurements a new chart displaced. Kept rather than deleted,
   │  │  │                      so a re-generate can never cost you ink on paper.
   │  │  └─ 2026-07-15_103000/  One displacement, stamped with the moment it happened — so
   │  │                         several re-generations never overwrite each other's history.
   │  └─ verifications/         Checks of the FINISHED profile, over time. The shared
   │     │                      verification chart lives here, and each check gets its own
   │     │                      dated folder, which is what lets a report show how the profile
   │     │                      holds up, or changes, month after month.
   │     ├─ 2026-07-15_1030/    One dated check: its measurement, and the folders below.
   │     │  ├─ chart/           A copy of the chart that check was measured with, so its
   │     │  │                   numbers stay tied to the sheet they came from.
   │     │  ├─ reads/           That check's individual readings, when it was averaged.
   │     │  ├─ reports/         The measurement report for that check, so each date keeps its
   │     │  │  │                own verdict alongside its readings.
   │     │  │  └─ old/          Earlier versions of that check's report, each in a folder
   │     │  │                   named with the moment it happened: the report as it read
   │     │  │                   before an Update rewrote it, and a report removed with “Delete
   │     │  │                   Selected Report”. The current report keeps its own name.
   │     │  └─ cache/           Working files from that check. Safe to delete, like every
   │     │                      other cache folder.
   │     ├─ exports/            The verification chart's hand-off files for other programs.
   │     ├─ reports/            Reports that cover SEVERAL of this run's checks at once — the
   │     │                      trend across dates, rather than any single one of them.
   │     └─ old/                Earlier verification charts, archived when the chart was
   │                            replaced. Your dated results are never moved.
   └─ run2/                     The next build, with exactly the same shape inside.
Your ChromIQ folder/            The folder your project folders live in: ~/ChromIQ, or your
│                               custom output folder from Settings. Beside the projects it can
│                               hold two folders of its own, made only when they are needed.
├─ reports/                     Measurement reports that cover measurements of more than one
│                               project. When those projects are not side by side in one
│                               folder, their report is always kept here, whichever folders
│                               the projects are in.
└─ old/                         Reports across several projects that were removed with “Delete
                                Selected Report”, each in a folder named with the moment it
                                happened. Moved here, never deleted.
ChromIQ's own settings folder/  Not inside any project. It holds what belongs to the APP
│                               rather than to one printer: on macOS
│                               ~/Library/Preferences/ChromIQ, on Windows %APPDATA%\ChromIQ,
│                               on Linux ~/.config/ChromIQ.
├─ presets/                     Your saved presets, one file per preset, in a folder per tab.
├─ compliance/                  The limit values of a paid standard, if you hold a copy and
│  │                            typed them in. They take the place of any ChromIQ ships.
│  └─ iso12647.json             Your own ISO 12647-7 and 12647-8 numbers. A number in it takes
│                               the place of the one ChromIQ ships for that row.
└─ reference_sets/              Your own copies of printing-condition reference data, which
   │                            ChromIQ prefers, set by set, over the copies it ships.
   ├─ SUPPLIED.json             ChromIQ's record of every reference file you supplied: where
   │                            it came from, when, and its checksum.
   └─ FOGRA61.txt               One supplied reference set, stored under ChromIQ's own name
                                for it rather than the name of the file you picked.

=== FILES RELATING TO FEATURES ===

  • Create Chart
      Input Files:  Your settings (or a loaded patch set / preset)
      Output Files: CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti1, CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti2, CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.channels.json, CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.strips.json, CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26_01.tif …; optional CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.pdf; the exports/ sidecars
  • Print Chart
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26_01.tif … (the chart pages)
      Output Files: CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ps (only on the PostScript print path)
  • Measure (profiling)
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti2 (+ CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.strips.json / .channels.json for the preview)
      Output Files: CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3; reads/readN.ti3 when averaging; reports/report_*.json when a measurement report is saved; plus chart/, a copy of the chart this run was measured with, saved the moment the measurement starts
  • Measure (verification)
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti2 (the shared verification chart, printed through the profile)
      Output Files: verifications/<date>/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti3 and its verifications/<date>/reports/report_*.json — one dated check, kept as history and never built into a profile; plus verifications/<date>/chart/, a copy of the chart that check was measured with, saved the moment the measurement starts
  • Build Profile
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3
      Output Files: CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.icc; merged.ti3 / merged.icc and calibrated.icc when refinement / calibration are used
  • Check & Refine
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3 and CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.icc
      Output Files: reports/Quality_Check_N_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt, reports/Refine_Strips_N_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt (beside the measurement when it is not in a ChromIQ project); with “Create X3DOM 3D visualisation (-w)” ticked: a 3D difference map, CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.x3d.html with x3dom.css and x3dom.js, beside the measurement
  • Create scanner or camera target
      Input Files:  A measurement of the chart (CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3 or a reference .cie/i1Profiler file)
      Output Files: CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.cht (recognition template) + CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.cie (reference values)
  • Build profile with scanner or camera
      Input Files:  Your scan or photo images + the chart's CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.cht and CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.cie
      Output Files: The scanner/camera ICC profile; cache/ working copies + a -diag.tif
  • Verify a profile (Tools)
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.icc and a verification CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti3 (the last step of a verification run: print through the profile → measure → report → this tool)
      Output Files: reports/Verify_Profile_N_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt (beside the measurement when it is not in a ChromIQ project)
  • Verify against reference (Tools)
      Input Files:  A profile / measurement and a reference
      Output Files: reports/Verify_Reference_N_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt (beside the measurement when it is not in a ChromIQ project)
  • Inspect a measurement (Tools)
      Input Files:  A measurement (.ti3), in a ChromIQ project or anywhere else
      Output Files: Only when you press “Save inspection…”: “Measurement inspection - CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26 - <date and time>.txt”, in the reports folder of what the measurement belongs to, or directly beside it outside a ChromIQ project. A folder you cannot write to is never offered.
  • Inspect a profile (Tools)
      Input Files:  A profile (.icc), in a ChromIQ project, in the system's profile folders or anywhere else
      Output Files: Only when you press “Save inspection…”: “Profile inspection - CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26 - <date and time>.txt”, filed by the same rule.
  • i1Profiler export (Tools)
      Input Files:  CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti1 / CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti2
      Output Files: exports/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-i1profiler.txt and .pxf
  • Create Chart (Run type = Verification)
      Input Files:  Your settings, or the run's profile when the chart is built From Profile Gamut
      Output Files: verifications/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti1 / .ti2 / .cht / .channels.json / _01.tif …, the same chart files a profiling chart gets; plus verifications/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.control-strip.json, which names the patches that stand in for a control strip; plus verifications/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify-reference.ti3 when the chart came From Profile Gamut
  • Print Chart (the print record)
      Input Files:  The chart's .ti2 and, when you print through a profile, that profile
      Output Files: CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.print.json beside the chart, recording how that sheet was printed: through the profile or raw, with which rendering intent, by which route, and which profile file. Written for any chart you print; on a verification run the Measurement Report reads it so it can state how a check was produced rather than assuming it
  • Measurement report (Tools)
      Input Files:  The run's measurements (CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3, or each verifications/<date>/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti3) with the chart's .ti2 beside them; a report you select, with the limit set and the other settings it was made with; and the chart's .control-strip.json where there is one
      Output Files: report_*.json in the reports folder that matches what the report covers, and a PDF beside it when you save one. Each report carries its own copy of the limits it was judged against, so it still reads correctly after the limits change
  • Report limits (from the Measurement Report)
      Input Files:  The limits of the report shown, and your own ISO values from compliance/iso12647.json when you have supplied them
      Output Files: Nothing into any report: a change is the report's own and is written when you press Generate report. Only the run's own default for new reports, when you choose one, goes into runs/runN/meta.json
  • Reference values (from Report limits)
      Input Files:  A file of ISO limit values you filled in, or a Fogra reference file (.txt or .zip) newer than the ones ChromIQ ships
      Output Files: compliance/iso12647.json, or a copy in reference_sets/ recorded in SUPPLIED.json. Nothing is written into your project

=== ALL FILE TYPES AND THEIR USE ===

WHAT THE FOLDERS MEAN

  • runs/run1, run2 …
      One folder per profile build; the newest is current. Old runs are your history — delete a whole runN if not needed.
  • runs/runN/reports/
      Things ChromIQ tells you about your PROFILING work: quality-check reports, the re-measure list, and the dated measurement reports for the profile build.
  • runs/runN/verifications/
      Checks of a FINISHED profile over time. The shared verification chart lives here, and each check gets its own dated sub-folder (verifications/2026-07-15_1030/ …) holding its measurement, its report, and (in a chart/ folder) a copy of the chart that check was measured with, so the results always stay tied to the sheet they came from. Kept apart from your profiling measurement, so the two never mix: this is what lets the Measurement Report trend how a profile holds up, or changes, month after month. Replacing the verification chart archives the old one to verifications/old/; your dated results stay where they are.
  • runs/runN/exports/
      Files made for use in other programs — the i1Profiler patch set and the plain colour list.
  • runs/runN/cache/
      Temporary working files from the tools. Always safe to delete — ChromIQ can recreate everything in here.
  • runs/runN/reads/
      Your individual readings when you measure a chart more than once to average.
  • cal/
      The optional printer-calibration target and its curves, shared by every run of this project. A project can contain this folder even when calibration options are switched off in Preferences — nothing is using it then, your charts and profiles are built without it, and switching calibration options back on makes it available again exactly as you left it. Nothing needs deleting.
  • cal/chart/
      A copy of the calibration chart exactly as it was printed, kept from the moment you start measuring it. “Restore Used Chart” puts this back, so you can reprint the sheet or read it again even after the chart has been regenerated.
  • cal/old/
      Earlier calibrations. Once a calibration has been measured, making a new calibration chart moves it here into a folder named with the date rather than deleting it, so an earlier .cal can always be read back — which is also what printcal's “Re-calibrate” and “Verify” modes compare against. A chart you never measured is replaced instead, in the same way a profile run's chart is. Each run also records which calibration it was built with, so ChromIQ can tell you which of them a given profile came from; runs made before ChromIQ started recording that simply say it is unknown.
  • cal/reports/
      The measurement reports of this project's calibration (Run type Calibration). “Delete Selected Report” moves one to cal/reports/old/<date>/.
  • exports/
      Files made for other programs from the Tools menu (project-wide, not tied to one run).
  • runs/runN/verifications/<date>/reports/old/
      Earlier versions of that dated check's reports, each in a folder named with the moment it happened. An Update keeps the version it replaces here, and “Delete Selected Report” moves a report here rather than deleting it. A report of one date that an Update widened to more dates leaves its old file here too. The current report keeps its own name.
  • compliance/  (in ChromIQ's settings folder, not in a project)
      The limit values of a paid standard, for a licence holder who has typed them in: one file, iso12647.json, holding your own ISO 12647-7 and 12647-8 numbers. A number in it takes the place of the value ChromIQ ships for that row; a row that standard puts no limit on reads “–” in the Report limits table, and the file does not change that. Put it in place from the Report limits window, under “Reference values…”; it is the same file on every machine you own, and deleting it simply puts back what ChromIQ ships.
  • reference_sets/  (in ChromIQ's settings folder, not in a project)
      Your own copies of printing-condition reference data, which ChromIQ prefers, set by set, over the eleven Fogra files it ships. A copy is stored under ChromIQ's own name for the set, never under the name of the file you picked, and SUPPLIED.json beside it records where each one came from, when, and its checksum. “Stop using it” removes ChromIQ's copy and leaves your original download alone.

THE THREE FILES THAT MATTER

  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26_01.tif, CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26_02.tif …  [runs/runN]
      The printable chart pages. Print these.
      Created by: Create Chart
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3  [runs/runN]
      Your measurements — the file the profile is built from. Keep it; any profile can be rebuilt later.
      Created by: Measure tab (on completion)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.icc  [runs/runN]
      Your finished ICC profile — the file you install or share.
      Created by: Build Profile tab

THE WORKING FILES OF A CHART (RUN FOLDER, TOP LEVEL)

  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti1  [runs/runN]
      The list of patch colours (the recipe, before it's laid out on paper).
      Created by: Create Chart (targen / generators)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti2  [runs/runN]
      The laid-out chart: which colour sits where. Measuring needs it.
      Created by: Create Chart
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.channels.json  [runs/runN]
      Records the ink channels and (for engine charts) the exact layout + recipe, so reopening restores everything.
      Created by: Create Chart
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.strips.json  [runs/runN]
      Exact per-strip and per-patch pixel positions, used by the Measure preview (arrow, click-to-jump, split patches).
      Created by: Create Chart (engine)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.pdf  [runs/runN]
      The chart as a vector PDF — only when “Also export a PDF” is ticked.
      Created by: Create Chart
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ps  [runs/runN]
      A PostScript copy for printing (bypasses colour management).
      Created by: Print Chart
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.cht / .cie  [runs/runN]
      The recognition template + reference values for reading a scanned or photographed chart. They stay next to the chart so the scanner tool finds them.
      Created by: Create scanner/camera target

REPORTS/ — THINGS CHROMIQ TELLS YOU

  • Quality_Check_1_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt  [runs/runN/reports]
      A readable quality report — grade, explanation, worst strips, full output. Numbered so checks don't overwrite each other.
      Created by: Check & Refine
  • Refine_Strips_N_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt  [runs/runN/reports]
      The list of strips to re-measure after a check; the guided refinement reads it back.
      Created by: Check & Refine
  • Verify_Profile_1_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt  [runs/runN/reports]
      A readable report from “Verify a profile” — verdict, scores, full output. Numbered so repeated checks keep a history.
      Created by: Verify a profile (Tools)
  • Verify_Reference_1_CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.txt  [runs/runN/reports]
      A readable report from “Verify against reference” — result summary and full output.
      Created by: Verify against reference (Tools)
  • Measurement inspection - CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26 - <date_time>.txt  [runs/runN/reports]
      Saved by Tools ▸ Inspect a measurement when you press “Save inspection…”.
      Created by: Inspect a measurement (Tools)
  • Profile inspection - CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26 - <date_time>.txt  [runs/runN/reports]
      The text of Tools ▸ Inspect a profile, saved the same way. For a profile in the system's profile folders the save window opens in your ChromIQ folder.
      Created by: Inspect a profile (Tools)
  • report_*.json  [runs/runN/reports]
      Dated PROFILING measurement reports (accuracy & trends), saved automatically after each measurement (Preferences → Reports). The Measurement Report tool reads these back (it builds its figures from the run's .ti3, needs the chart's .ti2 beside it for the ΔE, and reads the instrument name from the .ti3) and plots how the printer changes over time. Verification checks keep their own report points under verifications/<date>/reports/, gathered separately.
      Created by: Measure tab
  • report_*.json  [runs/runN/verifications/reports]
      A saved measurement report that covers SEVERAL dated checks of this run, made with “Generate report”. This one file is the whole report: which checks it covers, its report type, what it was judged against and each check's result in it. Nothing is written into the dates' own folders; each date's own report there is the one ChromIQ wrote after it was measured. “Delete Selected Report” moves this file to runs/runN/verifications/old/<date>/.
      Created by: Measurement Report tool
  • report_*.json  [cal/reports]
      A saved report of this project's calibration (Run type Calibration).
      Created by: Measure tab, Measurement Report tool
  • report_*.json  [reports (project folder)]
      A saved measurement report that covers measurements of SEVERAL profile runs of this project, for example checks of run1 and run2, or the profiling sheets of both. “Delete Selected Report” moves this file to old/<date>/ in the project folder. A report across projects is kept in the reports folder beside them, or in your ChromIQ folder's when they are not side by side.
      Created by: Measurement Report tool
  • <report title> - <date_time>.pdf  [reports/ — the one that matches the report's scope]
      A printable PDF of a measurement report, written when you press “Save report as PDF”. Its name is the report's own title, which you set in Preferences → Reports, followed by the moment it was written. It is filed with whatever the report covers, whichever window it was made in, so a report always sits beside the measurements it describes: ONE PROFILING RUN goes in that run's reports folder (runs/runN/reports/). ONE DATED CHECK goes in that date's own folder (runs/runN/verifications/<date>/reports/). SEVERAL CHECKS OF ONE RUN (the trend across dates) go in runs/runN/verifications/reports/. SEVERAL RUNS, or the whole profile, go in the project's own reports folder next to runs/. A CALIBRATION goes in cal/reports/. SEVERAL PROJECTS go in the reports folder beside them, or in your ChromIQ folder's when they are not side by side. A file from outside a project gets a reports folder beside it.
      Created by: Measurement Report tool

EXPORTS/ — FILES FOR OTHER PROGRAMS

  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-colours.txt  [runs/runN/exports]
      The chart's colours as a plain hex list (RGB charts). Can be pasted back into the New-chart dialog.
      Created by: Create Chart (best-effort)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-i1profiler.txt / .pxf  [runs/runN/exports]
      The patch set in i1Profiler's formats, for measuring with an i1iSis in i1Profiler.
      Created by: Create Chart (best-effort)

CACHE/ — TEMPORARY TOOL FILES (ALWAYS SAFE TO DELETE)

  • *-patchbox.cht, *-sample.cht  [runs/runN/cache]
      Prepared working copies of the recognition template the scanner tool reads instead of your original.
      Created by: Scanner/camera profiling
  • *-diag.tif  [runs/runN/cache]
      A diagnostic image showing where the tool found each patch — handy if recognition went wrong.
      Created by: Scanner/camera profiling

MEASURING, REFINING AND VERIFICATION

  • reads/read1.ti3, read2.ti3 …  [runs/runN/reads]
      Individual readings when you use “Measure again to average”; averaged back into CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3 when you finish.
      Created by: Measure tab
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.confirmed.json  [runs/runN]
      The patches confirmed as real (yellow outlines), so the preview shows them again after the measurement and on resuming. Ignored if the measurement changes.
      Created by: Measure tab
  • preconditioning.ti3 / .icc  [runs/runN]
      Copies of a previous run's measurement + profile, used to aim the next chart better.
      Created by: Refine
  • merged.ti3 / merged.icc  [runs/runN]
      The build-time merge of your new measurement with the pre-conditioning one. The installed profile still gets the clean CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.icc name.
      Created by: Build Profile (refinement)
  • calibrated.icc  [runs/runN]
      Your profile with calibration curves baked in (applycal), when the calibration workflow is on.
      Created by: Build Profile
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.x3d.html + x3dom.css / x3dom.js  [runs/runN]
      The 3D difference map Check & Refine writes when “Create X3DOM 3D visualisation (-w)” is ticked, next to the measurement it checked (the three files reference each other).
      Created by: Check & Refine

VERIFICATION RUNS — CHECKING A FINISHED PROFILE OVER TIME

  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti1 / .ti2 / .cht …  [runs/runN/verifications]
      The shared verification chart for this profile — usually smaller than the profiling chart (one page is plenty). You make it once on the Create Chart tab with Run type = Verification, and every future check reuses it, so results always compare like with like.
      Created by: Create Chart (Run type = Verification)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti1 / .ti2 / .channels.json …  [runs/runN/chart]
      A copy of the chart this profile run was measured with, kept so the measurement always describes a chart you still have. ChromIQ saves it automatically the moment a measurement starts. If you later change or re-create the chart, the “Restore Used Chart” button beside the Profile run brings this one back — your measurement is never touched. Only the chart's own files are copied: never the measurement, the profile or ChromIQ's own book-keeping.
      Created by: Measure tab (Run type = Profiling)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti1 / .ti2 / .channels.json …  [runs/runN/verifications/<date>/chart]
      A copy of the verification chart this dated check was measured with, kept so the results always describe a chart you still have. ChromIQ saves it automatically the moment a verification measurement starts. If you later change the verification chart, the “Restore Used Chart” button beside the Verification date puts this one back — your measurements are never touched. Page images are rebuilt from these files, and are stored here as well when the chart carries no layout recipe to rebuild them from.
      Created by: Measure tab (Run type = Verification)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.ti3  [runs/runN/verifications/<date>]
      One dated verification measurement: the verification chart printed THROUGH the profile (colour management ON) and measured, to see how accurate the profile still is. Each check lands in its own date-stamped folder, so nothing is overwritten. Tagged internally so it never builds a profile and never mixes with your profiling measurement.
      Created by: Measure tab (Run type = Verification)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.control-strip.json  [runs/runN/verifications]
      The chart's own declaration of which patches stand in for a printing control strip, written beside the chart the moment a verification chart is generated. It is what lets a report fill the three control-strip rows of its limit set instead of marking them N-A, and it is written ONLY beside a verification chart, never beside a profiling one. It travels into each dated check's chart/ copy, comes back with “Restore Used Chart”, and is archived and deleted with the chart it belongs to.
      Created by: Create Chart (Run type = Verification)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify-reference.ti3  [runs/runN/verifications]
      The colours this chart is SUPPOSED to be, written when the chart was built From Profile Gamut. Its presence is what tells ChromIQ the patches were already converted through the profile at build time, which is why such a chart prints Raw, and it is the yardstick the report measures against.
      Created by: Create Chart (From Profile Gamut)
  • CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-verify.print.json  [runs/runN/verifications]
      How that sheet was printed: through the profile or raw, with which rendering intent, by which route, and which profile file. ChromIQ writes one beside any chart you print, and on a verification run the Measurement Report reads it so that it can state how a check was produced rather than assuming it. A dated check keeps its own copy in that date's chart/ folder.
      Created by: Print Chart
  • report_*.json  [runs/runN/verifications/<date>/reports]
      The accuracy report for that one dated check. The Measurement Report tool trends the checks of a verification run over time, entirely separately from the profiling measurement above, so you can watch a profile hold up, or change, month after month.
      Created by: Measure tab (Run type = Verification)

STANDARDS, LIMITS AND REFERENCE DATA, OUTSIDE YOUR PROJECTS

  • iso12647.json  [compliance/ (ChromIQ's settings folder)]
      Your own ISO 12647-7 and 12647-8 limit values, if you hold a copy of the standards and typed them in. A number in it takes the place of the value ChromIQ ships for that row; a row that standard puts no limit on reads “–” in the Report limits table, and the file does not change that. Put it in place from the Report limits window, under “Reference values…”, which also writes you an empty template to fill in. Deleting it puts back what ChromIQ ships and changes nothing else.
      Created by: Reference values window
  • FOGRA39 … FOGRA60, SOURCE.json  [(inside the ChromIQ application)]
      The eleven Fogra reference sets ChromIQ ships, named FOGRA39_MW3_Subset.txt through FOGRA60_MW3_Subset.txt: tables of the colours a named printing condition aims for. SOURCE.json records where each one came from, the terms it travels under, and its checksum, which is re-read on every run so “distributed unmodified” is checkable rather than promised. These are reference data, not limits: a reference says what a colour should BE, a limit set says how far off it may be.
      Created by: Bundled with ChromIQ
  • FOGRAxx.txt, SUPPLIED.json  [reference_sets/ (ChromIQ's settings folder)]
      Your own copies of reference data, which ChromIQ prefers over the shipped ones, set by set. It stores each file under its own name for the set rather than the name of the file you picked, and SUPPLIED.json records where it came from, when, and its checksum. This is how a set published after your copy of ChromIQ reaches it without waiting for an update. “Stop using it” removes ChromIQ's copy; your original download is never touched.
      Created by: Reference values window

PROJECT-LEVEL FILES AND FOLDERS

  • project.json  [(project root)]
      ChromIQ's manifest: current run + run history. Please don't edit.
      Created by: Created on first use
  • meta.json  [runs/runN]
      Remembers the run's settings so reopening restores them.
      Created by: Each run
  • cal/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-cal.*  [cal]
      The calibration chart, its measurement (-cal.ti3) and curves (-cal.cal); the chart's own exports live in cal/exports.
      Created by: Calibration workflow
  • exports/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-i1profiler.*  [exports]
      i1Profiler exports made from the Tools menu.
      Created by: Tools menu
  • Where are my files.txt  [(project root)]
      This guide as a text file, updated when the folder layout changes. Edit or delete freely.
      Created by: Created on first use
  • scanner-test-targets/  [(output folder)]
      Next to your projects: every standard scanner target's layout file (.cht), yours to inspect or tweak — ChromIQ prefers the files here over its built-in copies, puts missing ones back, and never overwrites your edits. Demo scans land here too.
      Created by: Scanner/camera profiling

Safe to tidy: everything inside a cache folder is always safe to delete — ChromIQ can recreate all of it. The reports folders are safe to delete too, if you don't need the history of your quality checks. Your measurements (CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26.ti3, reads/, cal/CanonPro300_EpsPrSG_AdobeRGB_i1Studio_Okt26-cal.ti3) are real ink on real paper — keep those; any profile can be rebuilt from them later. The quickest big tidy-up is deleting whole runN folders you no longer need.